Power Tools 1993 November - Disc 2/Power Tools Plus (Disc 2 of 2)(November 1993)(HP).iso/hotlines/slidehl/hpcase/script.txt

Text File | 1992-07-20 | 22KB | 450 lines

HPCASEdge
**********
CASE01.GAL
**********
..picturea:\case01.GAL,61826,48452,1,67,21,

Good morning.  I'm really pleased to have this opportunity to give
you an overview of HP's CASE program called CASEdge.  I hope you'll
walk away with a good understanding of our approach and it is also
important that along the way you help me understand your software
development needs so we can see how we might be able to help.  I
think you'll find our approach different in a number of ways from
other suppliers.  You'll find it very practical in that it is based
on what we have learned from our own experiences,  it is fairly
broad in the scope of solutions available and it is based on
technology leadership.

It appears we have quite a range of expertise in this room, so
let's start with some definitions.
.PA
What is CASE
**********
CASE02.GAL
**********
..picturea:\case02.GAL,63821,48704,3,67,20,

People still struggle to define CASE and here are four different
ways the industry has been defining the tools and environments.
I think we could make life much simpler by saying CASE is software
to help people write software.  One school of thought is that CASE
is individual tools that cover different parts of the life cycle.
In the early days CASE was frequently viewed as just front-end
tools - tools that help you define requirements and do high level
design.  There are all kinds of categories being coined:  front-
end/back-end where back-end are the most widely used tools such as
editors, compilers and debuggers, then there is upper/lower and
big/little.  I am waiting for my favorite - inner and outer.  IBM
and DEC have defined CASE as being centered around a repository.
There are also a number of other solutions centered around one set
of tools and methodologies such as the world of Information
Engineering that both TI and Knowledgeware provide.  And finally
one of the categories that HP has defined and is now being
recognized by analysts such as Seybold and Gartner Group as the
real wave of the future and that is an integrating environment with
tool choices.

There is another view that says CASE is not just an environment or
a set of tools, but rather a process.
.PA
Software Engineering Process Evolution
**********
CASE03.GAL
**********
..picturea:\case03.GAL,65535,48704,1,67,20,

In other words CASE should be defined in terms of process maturity and
depending on where you are defines what you should be doing to get to
the next step.  The Software Engineering Institute defined 5 levels of
maturity starting with the initial, handcrafted stage (this is the
black magic stage), to the ultimate of an automatic process that is
continually feeding back on itself for full optimization.  Along the
way an organization is able to repeat a process and then move to a
level where they can transfer the process to another team and so on up
the chain.

So now that we've seen how the industry is defining CASE, let's
take a look at the problem we are trying to solve.
.PA
The Trouble With Our Times
**********
CASE04.GAL
**********
..picturea:\case04.GAL,65535,48323,1,68,20,

An old French philosopher had a very good way of describing the
problem.  There are so many factors that are causing companies to
reevaluate the way they do business - from increased global
competition to profit pressure.  Many companies are recognizing
that software development and maintenance costs are becoming a
large part of the cost of doing business and software is providing
a large part of the value they deliver to customers either directly
in products or through distribution, manufacturing and information
systems.  HP is no different.  70% of our R&D budget is for
software development.  It is a critical core competency.

So what are the software development needs.
.PA
Software Development Needs
**********
CASE05.GAL
**********
..picturea:\case05.GAL,65535,48145,1,68,20,

These three areas of investment protection, having an evolutionary
path to the future and improving the process are what we hear from
many of our customers as well as from our own divisions.  What are
your critical needs?  What is important to your business?

Now that we've got some definitions and have scoped the problem,
what is HP's program and how does it address these needs.
.PA
HP CASEdge
**********
CASE06.GAL
**********
..picturea:\case06.GAL,65535,48720,1,67,20,

At HP our CASEdge program embraces all of the industry definitions so
you can think of it as a TOTAL program.  It is practical since it is
built on the experience of 6,000 developers managing over 50 million
lines of code, and it is also based on HP's leadership in technology.
I'd like to take you through the 4 basic elements of HP's program
starting with HP's experience in software development as a foundation.
Then move to the knowledge layer which provides practical education,
training and consulting to improve the software development process.
The third piece is the technology HP has been driving standards in the
industry and which has led to major breakthroughs and finally the
tools and environment solutions that HP has available.  These three
types of solutions include the definitions we talked about earlier.
Standalone tools, integrated CASE or I-CASE is the one set of tools
and methodologies approach and open integration with tool choices.

Today the only repositories that are really being used for CASE
tool integration are those supplied by the I-CASE vendors as part
of their single toolset and some stand-alone toolsets which contain
their own databases.  IBM and DEC have not been able to deliver on
their promise of a general purpose repository for integrating
arbitrary CASE tools.  So that is how we map the 4 definitions we
talked about earlier with these 3 types of solutions.

Before we start discussing each layer of the CASEdge program,
let me give you a little more understanding of what this PRACTICAL
approach really means.
.PA
A Practical Approach
**********
CASE07.GAL
**********
..picturea:\case07.GAL,65535,48514,1,68,20,

There are four principles that drive our practical approach.  They are
the things that make us unique and these principals embody our
internal experience.  The first is to think differently about software
development.  It should be treated as an engineering process that can
be continuously improved.  And it takes a different mind set.  No
longer can software be changed at the last minute, you can expect zero
defects and software can be managed with predictable results.  How
many of you have sat in project review meetings where month after
month the project is 90% complete?  We've decided we won't take it
anymore.  Continuous, measurable improvements are the only way to go.
Some of you probably think HP is a computer company or at least laser
jet company, but we really are a voltmeter company.

After 50 years of instrumentation, we tend to measure everything
including software. It is in our blood.  The third principle is that
you simply can't throw everything out and start over.  There is so
much investment in hardware, software, methods, technics, etc. that
you have to bring the old forward with the new.  And finally we've
found that there isn't one size that fits all.  CASE solutions need to
be tailored depending on the type of software that is being developed
and the maturity level of the organization.  For example, if you are
developing an embedded real time system you need real time modeling
tools, cross compilers and debuggers and the ability to test the
system at speed.  If you are developing a business information system
you probably need data modeling tools that handle entity-relationship
diagrams, 4GL code generators and report writers.

Now let's move on to the first element of HP's CASEdge program, and
talk more specifically about software engineering at Hewlett- Packard.
.PA
Software Engineering at Hewlett-Packard
**********
CASE08.GAL
**********
..picturea:\case08.GAL,65535,49087,1,67,20,

Why is this important?  It is important because we are taking what
we learn (what works and what doesn't) and sharing those best
practices with you.  With over 70% of our R&D budget being spent
on software development, it is a critical core competency.  Our
goal is to: [read quote].  The key for us has been to treat
software as an engineering discipline and focus on continuous
improvement.  In the 80s, we had the 10X program to improve our
software quality by a factor of 10 over five years as measured by
post-release defect density and the number of critical and serious
defects.  This program began in 1986 and we did have some divisions
who achieved this goal.  Overall as a corporation we did not
totally achieve these goals, but we did achieve some significant
results. We developed extensive experience in establishing
baselines with our assessment process.  Our metrics leadership is
widely recognized in the industry.  The metrics book we published
in 1986 is now being followed by one on project management metrics
that will be on the shelves in May (1992). Divisions learned how
to focus on software defects, understand their real causes and then
make process changes based on what they found.  We have a new
software initiative (SWI) and are using a pilot approach of
attacking a real problem in a division by piloting an environment
with tools and methodologies and measuring the results.  Reuse and
maintenance are an important thrust of the program.
.PA
Knowledge
**********
CASE09.GAL
**********
..picturea:\case09.GAL,65535,48515,1,68,20,

The knowledge program is the second component of CASEdge.  It is
the vehicle we use to transfer these best practices and help our
customers improve their development process.  We've found that
focusing on tools alone will not solve the problem.  They are
certainly necessary, but not sufficient.  There are lots of
barriers and I think we've experienced them all - cultural,
organizational and process.  The knowledge component consists of
education, training and consulting services from both HP and other
suppliers that we work with.  This is a sampling categorized by the
type of solutions.  In the area of stand-alone tools courses on
languages, UNIX operating systems (which inludes HP-UX and MPE/iX)
and methods are offered.

In the I-CASE area there are a number of firms that consult on
methods and toolsets.  For open integration we also have customer
consulting to help you integrate a set of tools and automate your
own processes.  There is also a set of services that are
independent from the solution and can apply to any type of
approach. These include assessments which help you understand your
strengths and weaknesses and confidential recommendations are made.
Metrics consulting includes workshops or training your company to
teach it internally.

We don't have time to go into much depth now or talk about all of
our services, but we can follow-up on this later.
.PA
Driving Technology in CASE
**********
CASE10.GAL
**********
..picturea:\case10.GAL,65535,47940,1,68,20,

The third component of the CASEdge program is HP's leadership in
technology and driving key innovations in the areas of frameworks,
OO databases, languages and tools, and user interfaces for better
CASE solutions.  HP has pioneered the concept of an open
integrating framework for CASE - referred to as the toaster model
in the industry and has been endorsed by major industry bodies such
as ECME, CFI, IWCASE, NIST, and Sigma.

It consists of three types of integration - a common user interface
for all of the tools (or pieces or toast), an integration mechanism
that enables the tools to communicate with one another and automate
processes and the third is the layer that provides data integration
and repository services.  In the area of OO databases HP developed the
only OODB tuned for commercial applications and provides the first OO
SQL that connects legacy data and provides an object model for the old
and the new.  In languages HP chairs a number of ANSII committees -
one is C++.  HP also has taken a leadership role in defining OO Cobol.
In user interfaces HP has been a leader in making Motif a standard
through OSF.  The 3-D look and feel was initially designed for HP's
SoftBench environment. And since has been extended to include the
widely acclaimed desktop - HP VUE.

Now let's turn to the final component which are the solutions.
.PA
HP's CASEdge Solutions
**********
CASE11.GAL
**********
..picturea:\case11.GAL,65535,48323,1,68,20,

One way to characterize the 3 types of solutions available is to
look at the degree of flexibility and the level of integration and
structure that is provided.  With standalone tools you have a high
degree of flexibility and a low level of integration.  With I-CASE
you have a high degree of integration but little flexibility.  Open
integration combines a degree of flexibility with a degree of
integration.  Of course the industry is trying to achieve the best
of both.  So we expect you'll see I-CASE vendors becoming more open
and HP's open integration approach adding more integration.

And what about repositories? How do they fit in.  We talked earlier
that I-CASE environments have their own repository.  All tools in
the environment talk to the repository.  In the standalone world
you find what I call hot links are being developed. In other words
unique software is written that connects two tools together, but
there is no underlying infrastructure that would connect other
tools and it is usually a big job and you've got the N x N problem.
DEC with the CDD repository and IBM with Repository Manager have
been trying to implement a general repository for the past couple
of years with a select number of CASE tool suppliers.  Their
approach is to give you more tool choices, but you are still locked
in to their repository.  And customers claim the repositories do
not work yet.  The open integration solution is driving an industry
standard repository approach with IRDS and PCTE - the two most
promising standard definitions in the industry.
.PA
Standalone Tools
**********
CASE12.GAL
**********
..picturea:\case12.GAL,65535,48336,1,68,20,

In the area of standalone tools we have a wide variety that cover
all aspects of the software lifecycle. From analysis and design
through construction and test as well as project management,
documentation and configuration management. You probably can't read
this, but you can be pretty assured that the most widely used tools
are available on HP platforms.
.PA
Best-in-Class Integrated CASE
**********
CASE13.GAL
**********
..picturea:\case13.GAL,65535,48529,1,67,20,

In the area of I-CASE we have strategic relationships with a number
of best-in-class suppliers.  Historically I-CASE products have been
available only in commercial mainframe environments.  Therefore,
they are very well suited for developing complex business
applications.

CGI offers PACLAN for OS/2 development and PACLAN/X for HP-UX
development.  The CGI products can be used to target over 30
platforms, including HP-UX, MPE/iX, and MVS.  In addition each
supports a variety of methodologies, including SSADM and MERISE.
CGI is well-known for their premier COBOL code generator.
HP-UX is the first platform to have PACLAN/X available.
Maestro II is used for the HP-UX development environment and can
target multiple platforms.  It can support a number of methods and
is very strong in integrated project management support for large
teams.  TI's product targets HP-UX as well as MVS.  IEF supports
the James Martin Information Engineering methodology.
PowerCASE from Cognos does not cover as much of the life cycle as
other packages, but they have very strong native MPE/iX development
capability.  By the way, Cognos has recently renamed PowerCASE and
it is now called PowerDesigner.
.PA
Open Integration - HP SoftBench
**********
CASE14.GAL
**********
..picturea:\case14.GAL,65535,48911,1,67,20,

For open integration HP provides HP SoftBench.  HP SoftBench provides a
common user interface for all of the tools in the environment and
tool communication to automate parts of the software development
process.  For example, let's say you want to automatically build the
software system every time the software modules pass a complexity
test and achieve an 80% branch coverage.  If any of the software
modules do not pass, e-mail is automatically sent with the results
of the tests to the developer.  That is the time of automation that
is easily accomplished.  HP SoftBench has also been ported to other
platforms such as Sun and is the basis for IBM's AIX CASE program.
OpenCASE from Informix is the first open integration solution to
address 4GL development.  Siemens-Nixdorf and CDC have also
licensed HP SoftBench.  With over 10,000 installed SoftBench seats, it
is rapidly becoming an industry standard.

HP SoftBench is not just a framework but also a programming
environment for C and C++.  It comes with a basic set of integrated
tools today.  The encapsulation technology provides an easy way to
bring your existing tools into the environment as well as the best
in class tools available from independent software suppliers.
And easy here means days or weeks not months or years.
.PA
Best in Class ISV Tools
**********
CASE15.GAL
**********
..picturea:\case15.GAL,65535,48896,1,67,20,

So the basic environment can be extended to cover all aspects of
the lifecycle with encapsulated tools.  Here are some of the best
in class ISVs who are part of the SoftBench family and you can
pick and choose from the solutions that are available.  This
approach provides a way for you to tailor the solution to meet your
needs and gives you a growth path to more sophisticated solutions.
For example if you start out today with SCCS or RCS as your
configuration management capability, later on you can bring in a
more advanced package such as AMPLIFY/CONTROL or CCC and it should
be transparent to your development team.

Well if all of these choices are too overwhelming and you don't
know where to start, here is one way you might want to think about
them.
.PA
Where to Start
**********
CASE16.GAL
**********
..picturea:\case16.GAL,65535,48514,1,68,20,

This model has three dimensions that we've found to be useful in
helping to determining the right solution.  The first is the
process maturity of the organization represented by the axis on
the left and the second is by the type of application - whether
the data is the most important element of the application and is
modeled first or whether the logic of the software is what drives
the application.  The third dimension represented here is whether
there is mostly old software being maintained or whether there is
a substantial portion that is new development.  And, of course,
what complicates this is that data-driven applications are becoming
more on line oriented and logic-driven applications are frequently
dealing with processing large amounts of data.

We can explore this in more depth later, but let's try a couple of
examples.  One example would be that you are developing some new
logic-driven software, the team is very small and doesn't require
much formality in their process.  In this case it is possible that
an edit, compile, debug environment is all that is required to get
the job done.  But let's say you have a large team developing a new
logic-driven application or you have an application that requires
a very formal process (i.e. medical app, government contract,etc.).
You should probably look at an enivronment that will support front-
end design, formal testing and other parts of the software life
cycle.  If you are maintaining an existing application you should
probably look at reengineering solutions.  I think you get the
idea.  In addition I'm sure you'll want to consider the cost of
these various solutions which can vary considerably.

Again it all depends on your current situation and what you are
trying to accomplish.  Well, let me wrap up by giving you a quick
summary of the next steps of the CASEdge program.
.PA
HP CASEdge - The Next Steps
**********
CASE17.GAL
**********
..picturea:\case17.GAL,63595,47762,1,67,20,

We will be continuing to supply an even greater breadth of tools.
Tools to support migration, tools to help develop client/server
applications and tools that cover the entire software life cycle.
New tools are coming on the market everday and we want to assure
that you always have the best tools available.  For I-CASE we will
continue to work with our strategic suppliers and you can expect
announcements of some new relationships in the very near future.
In the area of open integration we will be increasing our support
of technical and business solutions.  For business applications you
will see support for COBOL tools. Data integration and data
repositories will become part of the HP SoftBench toaster model.
And you will see increasing life cycle coverage for object-oriented
development.

[Reuse HPCASEdge - A Total Practical Program Based on Leadership
and Experience slide for summary]

By now I hope you have seen that HP does have a total program, a
practical one based on HP's experience and one that is driving
innovation and standards through our technology contribution.  I'll
be happy to answer any further questions.